Skip to content

docs: inline Derive component and derive() string docs (6 files)#191

Closed
moss-bryophyta wants to merge 1 commit intomainfrom
docs/inline-derive-content
Closed

docs: inline Derive component and derive() string docs (6 files)#191
moss-bryophyta wants to merge 1 commit intomainfrom
docs/inline-derive-content

Conversation

@moss-bryophyta
Copy link
Copy Markdown
Collaborator

Summary

The <Derive> component and derive() string function documentation pages were rendering as empty on the live site. The template expansion from docs-templates/ was not working for these specific pages.

This PR inlines the full documentation content directly into the 6 affected files:

  • docs/en-US/next/api/components/derive.mdx
  • docs/en-US/react/api/components/derive.mdx
  • docs/en-US/react-native/api/components/derive.mdx
  • docs/en-US/next/api/strings/derive.mdx
  • docs/en-US/react/api/strings/derive.mdx
  • docs/en-US/react-native/api/strings/derive.mdx

Content is sourced from the existing templates with __PACKAGE_NAME__ and __DOCS_PATH__ substituted for each framework.

Reported by Ernest.

The template expansion was not rendering content for these pages.
Inlines the full documentation from docs-templates/ with package name
and docs path substitutions for next, react, and react-native.
@moss-bryophyta moss-bryophyta requested a review from a team as a code owner March 31, 2026 02:18
@moss-bryophyta moss-bryophyta enabled auto-merge (squash) March 31, 2026 02:18
@moss-bryophyta
Copy link
Copy Markdown
Collaborator Author

Closing — going to fix the template expansion instead of inlining.

auto-merge was automatically disabled March 31, 2026 02:21

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant